home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.20031118-20041115 / 000257_jaltman2@nyc.rr.com_Fri Apr 23 17:02:47 2004.msg < prev    next >
Internet Message Format  |  2020-01-01  |  12KB

  1. Path: newsmaster.cc.columbia.edu!panix!pln-e!lotsanews.com!cycny01.gnilink.net!cyclone1.gnilink.net!gnilink.net!cyclone.rdc-nyc.rr.com!news-out.nyc.rr.com!twister.nyc.rr.com.POSTED!not-for-mail
  2. Message-ID: <408984A3.8020104@nyc.rr.com>
  3. From: Jeffrey Altman <jaltman2@nyc.rr.com>
  4. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
  5. X-Accept-Language: en-us, en
  6. MIME-Version: 1.0
  7. Newsgroups: comp.protocols.kermit.misc
  8. Subject: Re: Does Kermit have stuff built-in for dialing-in to (TTS) Cortel-lines?
  9. References: <c6bt8p$83m$1@panix3.panix.com>
  10. In-Reply-To: <c6bt8p$83m$1@panix3.panix.com>
  11. Content-Type: text/plain; charset=us-ascii; format=flowed
  12. Content-Transfer-Encoding: 7bit
  13. Lines: 162
  14. Date: Fri, 23 Apr 2004 20:57:57 GMT
  15. NNTP-Posting-Host: 24.193.46.55
  16. X-Complaints-To: abuse@rr.com
  17. X-Trace: twister.nyc.rr.com 1082753877 24.193.46.55 (Fri, 23 Apr 2004 16:57:57 EDT)
  18. NNTP-Posting-Date: Fri, 23 Apr 2004 16:57:57 EDT
  19. Organization: Road Runner - NYC
  20. Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14974
  21.  
  22. It could be either a modem configuration problem or an incompatibility
  23. between your brand of modem and the modems used by Cortel on their
  24. lines.  If its a configuration problem I would look to drop the max
  25. speed of the modem to modem negotiations and ensure you have proper
  26. flow control settings.
  27.  
  28. Jeffrey Altman
  29. Secure Endpoints Inc
  30.  
  31.  
  32.  
  33.  
  34. David Combs wrote:
  35. > Hoping that maybe *something* in them will trigger
  36. > some memory or thought,
  37. > here's a copy of an email I sent to my shell-acct ISP, re
  38. > their dial-in somehow operating differently these days -- seems
  39. > it now uses TTS authentication, after I enter "panix.com" to
  40. > it's "host" prompt, simply says "authentication succeeded",
  41. > and instantly then hangs -- even before giving me an actual "Login" prompt.
  42. > Here's what I sent them:
  43. > Subject: [Mara] GlobalNAPS went down last night; need to make Cortel work *for me*                                                                           
  44. > From: David Combs <dkcombs@panix.com>                                                                                                                        
  45. > To: support@panix.com                                                                                                                                        
  46. > Date: Fri, 23 Apr 2004 15:50:38 -0400                                                                                                                        
  47. > Message-ID: <20040423195038.GA9685@panix.com>                                                                                                                
  48. >                                                                                                                                                              
  49. > Mara told me yesterday (email) that along with several                                                                                                       
  50. > other panix-users, Cortel-lines (the normal panix dial-ins)                                                                                                  
  51. > weren't suited, any more (since last week or two) for                                                                                                        
  52. > dial-in by me, and that I'd have to limit myself                                                                                                             
  53. > to the (few?) GlobalNAPS lines.                                                                                                                              
  54. >                                                                                                                                                              
  55. > Problem is that early this am, somewhere between                                                                                                             
  56. > 2am and 4am, it ceased allowing me to login,                                                                                                                 
  57. > simply hanging after I responded to its "host"                                                                                                               
  58. > prompt (I of course answered with the usual panix.com).                                                                                                      
  59. >                                                                                                                                                              
  60. > And without ability to dial in, no way to send email                                                                                                         
  61. > to support, since I have *no* way to get into panix.                                                                                                         
  62. >                                                                                                                                                              
  63. > And, weekend is coming up, ie unattended panix.                                                                                                              
  64. >                                                                                                                                                              
  65. > THUS:                                                                                                                                                        
  66. >                                                                                                                                                              
  67. > Whatever it is that makes Cortel unhappy with my                                                                                                             
  68. > dialing-in, I *must* surmount it.                                                                                                                            
  69. >                                                                                                                                                              
  70. > And only *you* guys can help me do that, by telling                                                                                                          
  71. > me what to change about my configuration (Blade100,                                                                                                          
  72. > solaris 9, coming in via Kermit (which I believe                                                                                                             
  73. > is pretty full-featured with security-stuff, or can                                                                                                          
  74. > at least probably let me use my own security-stuff, that                                                                                                     
  75. > comes with solaris.)).                                                                                                                                       
  76. >                                                                                                                                                              
  77. > My suggestion is that sometime before 8pm tonight (when                                                                                                      
  78. > I believe your final guy leaves for the weekend?), we                                                                                                        
  79. > talk by phone while I try suggestions from you                                                                                                               
  80. > and try to dial in via Cortel-lines.)                                                                                                                        
  81. >                                                                                                                                                              
  82. > If needed, let Alexis at least know about this                                                                                                               
  83. > suggestion.  I mean, if there's *several* of us                                                                                                              
  84. > having this Cortel-problem -- well, just how many                                                                                                            
  85. > GlobalNAPS lines does he want to pay for?                                                                                                                    
  86. >                                                                                                                                                              
  87. > Thanks,                                                                                                                                                      
  88. >                                                                                                                                                              
  89. > David                                                                                                                                                        
  90. >                                                                                                                                                              
  91. >              
  92. > ------------------------ And here's two earlier ones:
  93. > From dkcombs@panix.com Thu Apr 22 21:05:49 EDT 2004
  94. > Article: 76374 of panix.questions
  95. > From: dkcombs@panix.com (David Combs)
  96. > Newsgroups: panix.questions
  97. > Subject: (new to me) "TTS Authentication Succeeded" (or the like): then FREEZES (phone-dialin)
  98. > Date: 17 Apr 2004 17:34:08 -0400
  99. > For the last three or so weeks, I've been
  100. > dialing in through that "failsafe" line:
  101. >    dial 17185042681
  102. > Today I tried dialing in through a "regular" line,
  103. > the one in yonkers:
  104. >   1: yonkers:          dial 2332064
  105. > , and when I did, I got this "TTS Authenticated Succeeded"
  106. >  (or something close to that),
  107. > after which it "just sat there"  -- and after a few minutes
  108. > of fruitless waiting, I did the abort (kermit) control-\,
  109. > and reverted back to that "failsafe" (my terminology) line --
  110. > which works fine, no authenticationo message.
  111. > Needless to say, I've received no login-message (in the last three
  112. > or so weeks) that said anything about this TTS thing.
  113. > QUESTION: any idea what it wants me to do, to be able
  114. > to dial-in and *log-in* via the normal phone-lines?
  115. > Again, I'm coming in through plain dial-in, NOT via
  116. > cable-modem and browser and then into panix.  
  117. > Just a straight dial-in.
  118. > Thanks!
  119. > David
  120. > From staff@panix.com Thu Apr 22 21:05:56 EDT 2004
  121. > Article: 76413 of panix.questions
  122. > Path: reader2.panix.com!reader1.panix.com!panix!not-for-mail
  123. > From: staff@panix.com  (Mara's Staff Account)
  124. > Newsgroups: panix.questions
  125. > Subject: Re: (new to me) "TTS Authentication Succeeded" (or the like): then FREEZES (phone-dialin)
  126. > Date: Mon, 19 Apr 2004 13:24:04 +0000 (UTC)
  127. > dkcombs@panix.com (David Combs) writes:
  128. >  >For the last three or so weeks, I've been
  129. >  >dialing in through that "failsafe" line:
  130. >  >   dial 17185042681
  131. >  >Today I tried dialing in through a "regular" line,
  132. >  >the one in yonkers:
  133. >  >  1: yonkers:          dial 2332064
  134. >  >, and when I did, I got this "TTS Authenticated Succeeded"
  135. >  > (or something close to that),
  136. > Some users have problems with the Coretel (xx64) lines.
  137. > If you don't make  a successful connection on those lines 
  138. > you should use the GlobalNAPS numbers (what you referred to
  139. > as the "failsafe" line).  
  140. > Because dialup issues involve so many different variables, they
  141. > are usually better dealt with on an individual basis by email to
  142. > modems@panix.com.  Using a newsgroup is not particularly efficient.
  143.  
  144. -- 
  145. -----------------
  146. This e-mail account is not read on a regular basis.
  147. Please send private responses to jaltman at mit dot edu